Control device, sensor management device, control method, sensor management method and program

ABSTRACT

A communication unit acquires sensor-side metadata, which is information relating to a sensor, and application-side metadata, which is information relating to an application. A comparison unit extracts a sensor that can provide the sensing data through matching between the sensor-side metadata and the application-side metadata, and a notification unit transmits, based on a result of the extraction, a data flow control command to a sensor management device. The sensor-side metadata and the application-side metadata contain data that can be handled as dynamic data.

TECHNICAL FIELD

The present invention relates to a service for providing sensing datacollected by a sensor device or the like, and particularly relates to acontrol device, a sensor management device, a control method, a sensormanagement method, and a program.

BACKGROUND ART

Services for providing sensing data collected by a sensor device or thelike have gained attention in recent years. Patent Literature 1discloses a technique for delivering sensing data collected by a sensorfrom an appropriate provider to an appropriate user. In the techniquedisclosed in Patent Literature 1, matching is executed betweensensor-related information and information relating to an applicationthat uses sensing data, and a sensor is specified that can provide thesensing data required by the application. Then, the sensing datacollected by the specified sensor is transmitted to the application.Accordingly, with the technique disclosed in Patent Literature 1, it ispossible to deliver sensing data collected by a sensor to a user whorequires this sensing data.

CITATION LIST Patent Literature

Patent Literature 1: JP 5445722B

SUMMARY OF INVENTION Technical Problem

If services for delivering sensing data become widespread, sensing dataprovided by a larger number of providers needs to be able to be providedto a larger number of users. In this case, it is conceivable that, if anattempt is made to realize real-time matching, the processing load ofthe matching increases. For example, in the technique disclosed inPatent Literature 1, when matching for a sensor installed in a mobileobject is attempted, the mobile object moves from moment to moment, andthus the matching needs to be performed constantly in order to performcorrect matching of the position of metadata. In order to utilizehardware properties, a reduction in such a processing load forperforming matching is desirable. As a result of reducing the load ofprocessing for performing matching, it is expected that a sensor thatcan provide required sensing data can be easily specified, and deliveryof the sensing data is facilitated.

In view of the aforementioned circumstances, it is an object of thepresent invention to provide a control device, a sensor managementdevice, a control method, a sensor management method, and a program thatcan reduce the load of processing for performing matching betweensensor-related information and information relating to an applicationthat uses sensing data.

Solution to Problem

A control device according to one embodiment of the present inventionincludes: a first acquiring unit configured to acquire sensor-sidemetadata, which is information relating to a sensor that can outputsensing data; a second acquiring unit configured to acquireapplication-side metadata, which is information relating to anapplication that uses the sensing data; a comparison unit configured toexecute matching between the sensor-side metadata and theapplication-side metadata, and extract a sensor that can provide sensingdata that meets a request of the application; and an instruction unitconfigured to transmit, to a sensor management device that manages thesensor, a data flow control command that includes information that canspecify the sensor extracted by the comparison unit, and theapplication; wherein the sensor-side metadata contains information thatdesignates part of the metadata as being able to be handled as dynamicdata, the application-side metadata contains a condition that part ofthe metadata is required to be handled as dynamic data, and a dynamichandling condition, and the data flow control command includes thedynamic handling condition, and includes an instruction to instruct, ifthe sensing data that can be handled as dynamic data and is output bythe sensor or data that can be handled as dynamic data and is output byanother sensor attached to this sensor satisfies the dynamic handlingcondition, the corresponding sensor to transmit the sensing data to theapplication.

According to the control device having the above-describedconfiguration, it is possible to reduce the load of processing forperforming matching between information relating to a sensor andinformation relating to an application that uses sensing data.

The control device according to one embodiment of the present inventionmay be such that the comparison unit executes matching between a staticcomponent contained in the sensor-side metadata and the application-sidemetadata, and extracts the sensor that can provide the sensing data thatmeets the request of the application, and the instruction unittransmits, to the sensor management device, a data flow control commandthat includes a dynamic component of the sensor-side metadata that canbe used to determine whether or not the sensing data satisfies thehandling condition.

According to the control device having the above-describedconfiguration, it is possible to determine whether or not the sensingdata is to be transmitted to the application, by using a dynamiccomponent of the sensor-side metadata that can be used to determinewhether or not the sensing data satisfies the handling condition, andflexibly set the condition as to whether or not the sensing data is tobe transmitted, thus facilitating use of the sensing data.

The control device according to one embodiment of the present inventionmay be such that the comparison unit extracts a plurality of candidatesfor the sensor that can provide the sensing data that meets the requestof the application, and the data flow control command includes aninstruction to instruct any of the plurality of candidates to transmitthe sensing data that satisfies the handling condition to theapplication.

According to the control device having the above-describedconfiguration, it is possible to determine, from among a plurality ofsensors, a sensor that can provide sensing data that meets a request ofthe application.

The control device according to one embodiment of the present inventionmay be such that, if the application-side metadata matches a pluralityof pieces of sensor-side metadata, the instruction unit transmits thedata flow control command to a plurality of sensor management devicesthat correspond to the respective pieces of sensor-side metadata.

According to the control device having the above-describedconfiguration, it is possible to request the sensors that can transmitsensing data to provide sensing data that meets a request of theapplication, thus making it possible to increase the likelihood that thesensing data is provided.

The control device according to one embodiment of the present inventionmay be such that, if the sensor managed by one of the plurality ofsensor management devices transmits the sensing data, the instructionunit notifies the remaining at least one sensor management device ofcancellation of the instruction to deliver the sensing data.

According to the control device having the above-describedconfiguration, if at least one sensor transmits sensing data, thesensing data can be prevented from being redundantly transmitted fromanother sensor.

The control device according to one embodiment of the present inventionmay be such that the metadata contains a measurement item of the sensorthat is handled as dynamic data.

According to the control device having the above-describedconfiguration, sensing data can be provided based on a measurement itemof the sensor, and the condition as to whether or not the sensing datais to be transmitted can be flexibly set, thus facilitating use of thesensing data.

A sensor management device according to one embodiment of the presentinvention includes: a receiving unit configured to receive sensing dataoutput by a sensor; and a transmitting unit capable of transmitting thereceived sensing data to an application that uses the sensing data,wherein the receiving unit receives a data flow control command thatincludes information that can specify the application and the sensorthat is extracted through matching between sensor-side metadata, whichis information relating to a sensor that can output the sensing data,and application-side metadata, which is information relating to anapplication that uses the sensing data, the sensor-side metadatacontains information that designates part of the metadata as being ableto be handled as dynamic data, the application-side metadata contains acondition that part of the metadata is required to be handled as dynamicdata, and a dynamic handling condition, the data flow control commandincludes the dynamic handling condition, and if the sensing data thatcan be handled as dynamic data and is output by the sensor or data thatcan be handled as dynamic data and is output by another sensor attachedto this sensor satisfies the dynamic handling condition, thetransmitting unit transmits the sensing data to the application.

According to the sensor management device having the above-describedconfiguration, it is possible to reduce the load of processing forperforming matching between information relating to a sensor andinformation relating to an application that uses sensing data.

The sensor management device according to one embodiment of the presentinvention may be such that the receiving unit is capable of receivingsensing data output by a plurality of sensors, the transmitting unittransmits, out of the sensing data that can be handled as dynamic dataand is output by the sensors and the data that can be handled as dynamicdata and is output by the other sensors attached to these sensors,sensing data that satisfies the dynamic handling condition to theapplication.

According to the sensor management device having the above-describedconfiguration, it is possible to determine, from among a plurality ofsensors, a sensor that can provide sensing data that meets a request ofthe application.

The sensor management device according to one embodiment of the presentinvention may further include a storage unit configured to store thesensing data received by the receiving unit, the sensing data being thesensing data that can be handled as dynamic data and is output by thesensor, or the data that can be handled as dynamic data and is output bythe other sensor attached to this sensor, wherein the transmitting unittransmits the sensing data that satisfies the dynamic handling conditionto the application, with reference to the storage unit.

According to the sensor management device having the above-describedconfiguration, it is possible to temporarily store sensing data outputfrom a sensor or data output from another sensor, and provide sensingdata that meets a request of the application, based on previous data.

The sensor management device according to one embodiment of the presentinvention may further include a detection unit configured to detect thatthe sensing data received by the receiving unit satisfies the dynamichandling condition, the sensing data being the sensing data that can behandled as dynamic data and is output by the sensor, or the data thatcan be handled as dynamic data and is output by the other sensorattached to this sensor, wherein, if it is detected by the detectionunit that the dynamic handling condition is satisfied, the transmittingunit transmits the sensing data that satisfies the dynamic handlingcondition to the application.

According to the sensor management device having the above-describedconfiguration, it is possible to reduce the load of processing forperforming matching between information relating to a sensor andinformation relating to an application that uses sensing data.

The sensor management device according to one embodiment of the presentinvention may be such that, if the sensing data that satisfies thedynamic handling condition is transmitted to the application, thetransmitting unit notifies a control device that transmitted the dataflow control command of the transmission of the sensing data.

According to the sensor management device having the above-describedconfiguration, if at least one sensor transmits sensing data, thesensing data can be prevented from being redundantly transmitted fromanother sensor.

A control method according to one embodiment of the present inventionincludes: a first acquiring step of acquiring sensor-side metadata,which is information relating to a sensor that can output sensing data;a second acquiring step of acquiring application-side metadata, which isinformation relating to an application that uses the sensing data; acomparing step of executing matching between the sensor-side metadataand the application-side metadata, and extracting a sensor that canprovide sensing data that meets a request of the application; and aninstructing step of transmitting, to a sensor management device thatmanages the sensor, a data flow control command that includesinformation that can specify the sensor extracted by the comparisonunit, and the application, wherein the sensor-side metadata containsinformation that designates part of the metadata as being able to behandled as dynamic data, the application-side metadata contains acondition that part of the metadata is required to be handled as dynamicdata, and a dynamic handling condition, the data flow control commandincludes the dynamic handling condition, and includes an instruction toinstruct, if the sensing data that can be handled as dynamic data and isoutput by the sensor or data that can be handled as dynamic data and isoutput by another sensor attached to this sensor satisfies the dynamichandling condition, the corresponding sensor to transmit the sensingdata to the application.

According to the control method having the above-describedconfiguration, it is possible to reduce the load of processing forperforming matching between information relating to a sensor andinformation relating to an application that uses sensing data.

A program according to one embodiment of the present invention causes acomputer to execute: a first acquiring step of acquiring sensor-sidemetadata, which is information relating to a sensor that can outputsensing data; a second acquiring step of acquiring application-sidemetadata, which is information relating to an application that uses thesensing data; a comparing step of executing matching between thesensor-side metadata and the application-side metadata, and extracting asensor that can provide sensing data that meets a request of theapplication; and an instructing step of transmitting, to a sensormanagement device that manages the sensor, a data flow control commandthat includes information that can specify the sensor extracted by thecomparison unit, and the application, wherein the sensor-side metadatacontains information that designates part of the metadata as being ableto be handled as dynamic data, the application-side metadata contains acondition that part of the metadata is required to be handled as dynamicdata, and a dynamic handling condition, the data flow control commandincludes the dynamic handling condition, and includes an instruction toinstruct, if the sensing data that can be handled as dynamic data and isoutput by the sensor or data that can be handled as dynamic data and isoutput by another sensor attached to this sensor satisfies the dynamichandling condition, the corresponding sensor to transmit the sensingdata to the application.

According to the program having the above-described configuration, it ispossible to reduce the load of processing for performing matchingbetween information relating to a sensor and information relating to anapplication that uses sensing data.

A sensor management method according to one embodiment of the presentinvention includes: a receiving step of receiving sensing data output bya sensor; and a transmitting step capable of transmitting the receivedsensing data to an application that uses the sensing data, wherein, inthe receiving step, a data flow control command is received, the dataflow control command including information that can specify theapplication and the sensor that is extracted through matching betweensensor-side metadata, which is information relating to a sensor that canoutput the sensing data, and application-side metadata, which isinformation relating to an application that uses the sensing data, thesensor-side metadata contains information that designates part of themetadata as being able to be handled as dynamic data, theapplication-side metadata contains a condition that part of the metadatais required to be handled as dynamic data, and a dynamic handlingcondition, the data flow control command includes the dynamic handlingcondition, and in the transmitting step, if the sensing data that can behandled as dynamic data and is output by the sensor or data that can behandled as dynamic data and is output by another sensor attached to thissensor satisfies the dynamic handling condition, the sensing data istransmitted to the application.

According to the sensor management method having the above-describedconfiguration, it is possible to reduce the load of processing forperforming matching between information relating to a sensor andinformation relating to an application that uses sensing data.

A program according to one embodiment of the present invention causes acomputer to execute: a receiving step of receiving sensing data outputby a sensor; and a transmitting step capable of transmitting thereceived sensing data to an application that uses the sensing data,wherein, in the receiving step, a data flow control command is received,the data flow control command including information that can specify theapplication and the sensor that is extracted through matching betweensensor-side metadata, which is information relating to a sensor that canoutput the sensing data, and application-side metadata, which isinformation relating to an application that uses the sensing data, thesensor-side metadata contains information that designates part of themetadata as being able to be handled as dynamic data, theapplication-side metadata contains a condition that part of the metadatais required to be handled as dynamic data, and a dynamic handlingcondition, the data flow control command includes the dynamic handlingcondition, and in the transmitting step, if the sensing data that can behandled as dynamic data and is output by the sensor or data that can behandled as dynamic data and is output by another sensor attached to thissensor satisfies the dynamic handling condition, the sensing data istransmitted to the application.

According to the program having the above-described configuration, it ispossible to reduce the load of processing for performing matchingbetween information relating to a sensor and information relating to anapplication that uses sensing data.

Advantageous Effects of Invention

According to the control device, the sensor management device, thecontrol method, the sensor management method, and the program of thepresent invention, it is possible to reduce the load of processing forperforming matching between information relating to a sensor andinformation relating to an application that uses sensing data.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a diagram schematically illustrating a data providing system 1according to a first embodiment of the present invention.

FIG. 2 is a diagram illustrating an example of a configuration of thedata providing system 1 according to the first embodiment of the presentinvention.

FIG. 3 is a diagram illustrating an example of a configuration of acontrol device 2 according to the first embodiment of the presentinvention.

FIG. 4 is a diagram illustrating an example of a configuration of asensor management device 3 according to the first embodiment of thepresent invention.

FIG. 5 is a flowchart illustrating an example of an operation of thecontrol device 2 according to the first embodiment of the presentinvention.

FIG. 6 is a flowchart illustrating an example of an operation of thesensor management device 3 according to the first embodiment of thepresent invention.

FIG. 7 is a diagram illustrating an example of an operation of the dataproviding system 1 according to a working example 1 of the firstembodiment of the present invention.

FIG. 8 is a diagram illustrating an example of a configuration ofsensor-side metadata according to the working example 1 of the firstembodiment of the present invention.

FIG. 9 is a diagram illustrating an example of a configuration ofapplication-side metadata according to the working example 1 of thefirst embodiment of the present invention.

FIG. 10 illustrate examples of configurations of sensor-side metadataand application-side metadata, according to a working example 2 of thefirst embodiment of the present invention.

FIG. 11 illustrate other examples of the configurations of sensor-sidemetadata and application-side metadata, according to the working example2 of the first embodiment of the present invention.

FIG. 12 illustrate yet other examples of the configurations ofsensor-side metadata and application-side metadata, according to theworking example 2 of the first embodiment of the present invention.

FIG. 13 is a diagram illustrating an example of a configuration of adata providing system 1 according to a second embodiment of the presentinvention.

FIG. 14 is a diagram illustrating an example of a configuration of acontrol device 2 according to the second embodiment of the presentinvention.

FIG. 15 illustrate examples of configurations of sensor-side metadataaccording to the second embodiment of the present invention.

FIG. 16 is a sequence diagram illustrating an example of an operation ofthe data providing system according to the second embodiment of thepresent invention.

DESCRIPTION OF EMBODIMENTS First Embodiment

A first embodiment of the present invention will be described withreference to the drawings.

FIG. 1 is a diagram showing an overview of a data providing system 1according to the first embodiment of the present invention. As shown inFIG. 1, the data providing system 1 can provide a service for mediatingbetween a data provider that provides data, and a data user who uses thedata.

The data providing system 1 performs matching between sensing data thatis provided by a data provider and sensing data that is desired to beused by the data user, and delivers, if matching therebetween issuccessful, the sensing data provided by the data provider to the datauser.

First, the data providing system 1 receives, from a data provider, (1)registration of “sensor-side metadata” that indicates the content ofsensing data that can be provided by the data provider. Note that thenumber of data providers is not limited to one, and there may be aplurality of data providers. Then, the data providing system 1 receives,from a data user, (2) registration of “application-side metadata” thatindicates the content of sensing data that is desired to be used by thedata user. Note that the data user uses the sensing data in anapplication server, for example.

Then, the data providing system 1 executes (3) matching between theregistered sensor-side metadata and the registered application-sidemetadata, and determines whether or not there is sensing data that meetsa request of the data user. Then, the data providing system 1 causes acontrol device 2 to give (4) a “data flow control command”, which isinformation relating to sensing data delivery, to a device that managesa sensor. Then, based on the “data flow control command”, the dataproviding system 1 performs (5) delivery of the sensing data provided bythe data provider to the data user.

Here, the data flow control command includes information that specifiesa sensor, serving as a data source from which data is provided, and anapplication, serving as a data destination at which the data is used,and is command information for instructing data delivery from the datasource to the data destination. The present invention is characterizedin that the data flow control command further includes a later-describedevent condition.

As described above, the data providing system 1 provides a service forperforming matching between sensing data that is provided by a dataprovider and sensing data that is desired to be used by a data user, anddelivering the sensing data based on a result thereof. Accordingly, thedata user can easily specify, from among a large number of dataproviders, a data provider that can provide the sensing data that meetshis or her request. Furthermore, the data providing system 1 can alsoreduce time taken and the effort made by the data provider to search fora data user who desires to use the sensing data provided by the dataprovider. In this way, the data providing system 1 can facilitate use ofsensing data.

Here, “metadata” used in matching refers to attribute information ofsensing data. For example, “metadata” is data to be registered by a dataprovider or a data user, such as a data item, a format specification,and a money charging specification of sensing data. “Metadata” includesdata necessary for a user to make a determination regarding a datapurchasing contract.

Metadata may also include items such as “who”, “what”, “where”, “when”,“how”, and “how much”. “Who” means a data provider, and is informationrelating to a given business operator or person. “What” is informationrelating to a category, a measurement object, and an attribute of themeasurement object of sensing data, and the like. “Where” is informationindicating a position or a location where measurement was performed. Theinformation encompasses mobile-type information and fixed-typeinformation, and in the mobile-type information, a measurement positionchanges with spatial movement of a sensing device, whereas in thefixed-type information, a measurement position is fixed and does notchange.

Furthermore, “when” is information relating to time at which measurementwas performed. The information encompasses instantaneous information andperiodic information, and in the instantaneous information, a data value(of speed, for example) is determined by a one-time measurement, whereasin the periodic information, a data value (of electric power, forexample) is determined by a measurement taken in a predetermined timeperiod. Furthermore, “how” is information relating to a sensing device(sensor), such as a sensing device specification, a formatspecification, measurement conditions, and setting conditions.Furthermore, “how much” is information relating to conditions when moneyis charged, such as a settlement method, a charging method, and theamount of money.

In the data providing system 1, the data provider releases, to thepublic, at least some of the information of sensing data that the dataprovider can provide, so that a user can reference them. Also, the datauser designates at least some of this information, and specifies thesensing data that he or she desires to use.

Here, in the first embodiment of the present invention, “metadata” mayalso be sensing data itself. In this case, “metadata” may also be data(event data) of the sensing data that changes every time a measurementis made. For example, “metadata” may also be “temperature”, which issensing data in the case of a thermometer. In this case, for example,the sensor-side metadata contains an item “temperature” that changesfrom moment to moment, and in the application-side metadata, an “eventcondition” such as for example “30 degrees or higher”, can be set.

The data providing system 1 uses the event data (temperature) of thesensing data to be delivered from the sensor to determine whether or notit satisfies the “event condition” (30 degrees or higher). If the eventdata satisfies the event condition, the sensing data will be deliveredfrom the data provider to the data user, and otherwise, no sensing datawill be delivered.

As described above, the first embodiment of the present invention is anembodiment in which sensor-side metadata contains “event data”, andapplication-side metadata contains an “event condition”. The dataproviding system 1 according to the first embodiment of the presentinvention references the “event data” of the sensing data, determineswhether or not it satisfies the “event condition”, and controls whetheror not the sensing data needs to be delivered.

However, when sensor-side metadata contains “event data” andapplication-side metadata contains an “event condition”, there is a riskthat, if the control device 2 shown in FIG. 1 executes matching, theprocessing load on the control device 2 may drastically increase. Thisis because, every time the “event data” of the sensor-side metadata isupdated, the control device 2 has to receive (1) registration of theupdated sensor-side metadata, execute (3) matching between theregistered sensor-side metadata and the application-side metadata, anddetermine whether or not there is sensing data that satisfies a requestof the data user. For example, if the “event data” of the sensor-sidemetadata is, for example, temperature or electric power that is measuredat an interval of one second or the like, matching will need to beexecuted every second, thus resulting in an increase in the processingload on the control device 2.

Also, the control device 2 needs to execute matching between sensor-sidemetadata and application-side metadata for a plurality of pairs, ratherthan only needing to execute matching for one pair. Accordingly, thereis a risk that the control device 2 will need to execute, at the sametime, multiple matching operations at a short interval, and in thiscase, the processing load will drastically increase.

Accordingly, in the first embodiment of the present invention, thecontrol device 2 performs, in advance, matching based on staticinformation contained in the sensor-side metadata and theapplication-side metadata, and then the sensor management device 3determines whether or not the “event data” satisfies the “eventcondition”, and judges whether or not the sensing data needs to bedelivered.

In this way, the processing load required for matching can be dispersedbetween the control device 2 and the sensor management device 3. Also,the control device 2 does not need to execute matching of “event data”,which changes dynamically, and thus it is possible to suppress anincrease in the processing load. On the other hand, a sensor managementdevice 3 is provided for each sensor (or for each attribute of thesensor), and thus the sensor management device 3 is less likely toexecute matching of “event data”, which changes dynamically, for aplurality of pairs, and even if the is the case, it is conceivable thatthe number of pairs will be small. Accordingly, the processing load ofthe sensor management device 3 is also less likely to drasticallyincrease. Accordingly, in the first embodiment of the present invention,it is possible to prevent a drastic increase in the processing load onthe control device 2, and even if “event data”, which changesdynamically, is used as a condition for matching, it is possible todeliver sensing data from a data provider to a data user, thusfacilitating use of the sensing data.

Example of System Configuration

FIG. 2 is a diagram showing an example of a configuration of the dataproviding system 1 according to the first embodiment of the presentinvention. As shown in FIG. 1, the data providing system 1 includes thecontrol device 2, the sensor management device 3, the sensor 4, and theapplication server 5.

The control device 2 is a device that executes matching betweensensor-side metadata and application-side metadata. The control device 2is, for example, a so-called server device or a computer (such as adesktop computer, a laptop computer, or a tablet, for example). Notethat the control device 2 is not limited to these examples.

The control device 2 acquires, from a data provider, sensor-sidemetadata, which is attribute information of sensing data. Thesensor-side metadata is, for example, information relating to a sensorthat can output sensing data. The sensor-side metadata includes, as theinformation relating to sensing data, at least some of a category, ameasurement object, a measurement item, a measurement location, ameasurement time of the sensing data, and the like, for example. Notethat the sensor-side metadata is not limited to these examples, and mayinclude any information as long as it relates to sensing data. Note thatthe sensor-side metadata may also be, for example, part of the sensingdata itself. The sensor-side metadata can be created by a data providerfor example, and may be transmitted to the control device 2 via a device(not-shown) usable by a data user, or may be directly input to thecontrol device 2.

In the first embodiment of the present invention, the sensor-sidemetadata contains data (event data) of the sensing data that changesevery time a measurement is made. The sensor-side metadata may alsocontain event data, which is data that changes every time a measurementis made, such as “temperature” that changes from moment to moment, a“still view image” captured from a mobile object, or “electric power”generated through photovoltaic power generation, for example. Note thatthe event data is not limited to these examples, and may be any data aslong as it changes every time a measurement is made.

Furthermore, the control device 2 acquires, from a data user,application-side metadata that indicates content of sensing data desiredto be used by the data user. The application-side metadata is, forexample, information relating to an application that uses the sensingdata. For example, the application-side metadata includes, as theinformation relating to sensing data desired to be used, at least someof a category, a measurement object, a measurement item, a measurementlocation, and a measurement time of the sensing data desired to be used,and the like. Note that the application-side metadata is not limited tothese examples, and may include any information as long as it relates tosensing data. The application-side metadata can be created by the datauser, and may be transmitted to the control device 2 via the applicationserver 5, or may be directly transmitted to the control device 2.

In the first embodiment of the present invention, the application-sidemetadata contains a condition (event condition) relating to informationthat changes dynamically. In other words, the application-side metadatacontains an “event condition”. “Event condition” is a condition relatingto information that changes dynamically, and examples thereof include acondition for a measurement location and a condition for measurementtime. The application-side metadata contains, as the “event condition”,“when the temperature is 30 degrees or higher”, “when the generatedelectric power is 1 W or greater”, and the like, for example. Theinformation that changes dynamically may also contain data that changesevery time a measurement is made, that is, event data, and the “eventcondition” may also be a condition relating to event data. Note that theinformation that changes dynamically is not limited to these examples,and may be any information as long as it changes dynamically.

The control device 2 executes matching between the sensor-side metadataand the application-side metadata. The control device 2 determines thatthe matching is successful if, for example, there is sensor-sidemetadata that matches the application-side metadata. The control device2 may also determine that the matching is successful if, for example, atleast some of the sensor-side metadata matches at least some ofinformation contained in the application-side metadata. Furthermore, thecontrol device 2 may also determine that the matching is successful if,for example, there is sensor-side metadata that satisfies apredetermined condition contained in the application-side metadata.

In the first embodiment of the present invention, the control device 2can perform matching based on static information (static components)contained in the sensor-side metadata and the application-side metadata.For example, the control device 2 determines that the matching issuccessful based on static information (static components) such as a“category”, a “data delivery entity”, or “measurement object name” thatare contained in both the sensor-side metadata and the application-sidemetadata.

If the matching is successful, the control device 2 then gives, to thesensor management device 3, a “data flow control command” that includesinformation relating to a sensor (sensor-related information), andinformation relating to an application that uses sensing data(application-related information). The sensor-related information is,for example, an identifier that can identify a sensor that transmits thesensing data, and is used to specify the sensor. Furthermore, theapplication-related information is, for example, an identifier that canidentify an application that uses the sensing data, and is used tospecify the application.

In the first embodiment of the present invention, the data flow controlcommand may also include information, of the sensing data, relating todata that changes every moment or data (event data) that changes everytime a measurement is made, both types of data being contained in thesensor-side metadata. Furthermore, the data flow control command mayalso include an “event condition”, which is a condition that relates toinformation that changes dynamically, and is contained in theapplication-side metadata. The “event condition” is, for example, acondition that is contained in the application-side metadata and relatesto information (including event data) that changes dynamically. Notethat the event data is not limited to data of sensing data that changesevery moment or every time a measurement is made, and may be data thatchanges every moment or every time a measurement is made, obtained byanother sensor different from the sensor that collects the sensing data.For example, the event data may also be a condition that relates to animage itself captured by a camera, which is a sensor, or a conditionthat relates to data of another sensor such as a global positioningsystem (GPS) attached to this camera.

The sensor management device 3 is a device that delivers sensing datafrom the sensor 4 to the application server 5 in accordance with aninstruction (data flow control command) from the control device 2. Thesensor management device 3 is, for example, a so-called server device ora computer (such as a desktop computer, a laptop computer, or a tablet,for example). Note that the sensor management device 3 is not limited tothese examples.

Based on the data flow control command received from the control device2, the sensor management device 3 instructs the sensor 4 to deliver thesensing data to the application server 5. The sensor management device 3specifies, based on the sensor-related information contained in the dataflow control command, the sensor 4 from which the sensing data is to beacquired. Furthermore, the sensor management device 3 specifies, basedon the information relating to the application server 5 that iscontained in the data flow control command, the application server 5 towhich the sensing data is to be delivered. The sensor management device3 instructs the specified sensor 4 to deliver the sensing data to thespecified application server 5.

Furthermore, the sensor management device 3 may also instruct the sensor4 to “deliver the sensing data to the application server 5”, ifinformation relating to event data satisfies an event condition. Forexample, if data (event data) of the sensing data that changes everymoment or every time a measurement is made satisfies the eventcondition, the sensor management device 3 may also instruct the sensor 4to deliver the sensing data to the application server 5. For example, ifa temperature (event data) detected by a thermometer, which is a sensor,satisfies a condition (event condition) of being 30 degrees or higher,the sensor management device 3 may also instruct the thermometer, whichis a sensor, to deliver the temperature to the application server 5.

Furthermore, the sensor management device 3 may also instruct the sensor4 to deliver the sensing data to the application server 5, if, forexample, another piece of data that relates to the sensing data andchanges every moment or every time a measurement is made satisfies anevent condition. For example, if data of a GPS, which is another sensor7 attached to a camera, satisfies an event condition (for example,within a radius of 20 m from the front of Nijo-jo Castle), the sensormanagement device 3 may also instruct the camera to deliver a capturedimage to the application server 5.

The sensor 4 is a device that collects sensing data. The sensor 4 may beany device as long as it can collect data. The sensor 4 may also be anydevice such as, for example, a camera that can collect images, movingimages, and the like, a thermometer/hygrometer that can measure, forexample, a temperature/humidity, a rain gauge/wind gauge that canmeasure rainfall/wind speed, or a GPS that can measure a location.

The application server 5 is a device that can use sensing data. Theapplication server 5 is, for example, a so-called server device or acomputer (such as a desktop computer, a laptop computer, or a tablet,for example), a smartphone or a mobile phone (for example, a featurephone), a computer (such as a desktop computer, a laptop computer, or atablet, for example), a personal digital assistant (PDA), a wearableterminal, or the like. Note that the application server 5 is not limitedto these examples.

The application server 5 can use sensing data to provide various typesof services. For example, the application server 5 can use a still viewimage, serving as sensing data, to provide a service relating to virtualsightseeing. “Virtual sightseeing” enables, for example, a user in Tokyoto have an experience, with a view of the city of Kyoto displayed on hisor her smartphone, as if he or she is sightseeing in Kyoto. Note thatthe service that the application server 5 can provide is not limited tovirtual sightseeing, and may be any service.

Note that the control device 2, the sensor management device 3, thesensor 4, and the application server 5 may be connected to each othervia a not-shown network (NW) 6. The NW 6 is, for example, a wirednetwork or a wireless network. Specifically, the NW 6 is a wireless LAN(WLAN), a wide area network (WAN), an integrated service digital network(ISDN), a wireless LAN, a long term evolution (LTE) network, a codedivision multiple access (CDMA) network, or the like. Note that the NW 6is not limited to these examples, and may be, for example, a publicswitched telephone network (PSTN) or Bluetooth (registered trademark),or satellite-based communication, and may be any type of NW.

Example of Configuration of Control Device 2

FIG. 3 is a diagram showing an example of a configuration of the controldevice 2 according to the first embodiment of the present invention. Asshown in FIG. 3, the control device 2 includes a communication unit 20,a control unit 21, a sensor-side metadata storage unit 25, and anapplication-side metadata storage unit 26.

The communication unit 20 is a communication interface for connection tothe sensor management device 3, the sensor 4, and the application server5. The control device 2 transmits a data flow control command to thesensor management device 3 via the communication unit 20. Furthermore,the control device 2 receives sensor-side metadata or application-sidemetadata via the communication unit 20. The communication executed bythe communication unit 20 may be wired communication or wirelesscommunication, and may employ any communication protocol.

The communication unit 20 functions as a first acquiring unit forreceiving sensor-side metadata, and a second acquiring unit forreceiving application-side metadata. In the example of FIG. 3, onecommunication unit 20 has both functions of the first acquiring unit forreceiving sensor-side metadata, and the second acquiring unit forreceiving application-side metadata, but the first acquiring unit andthe second acquiring unit may also be provided as separateconfigurations (separate interfaces).

The control unit 21 functions to execute matching between sensor-sidemetadata and application-side metadata. The control unit 21 has thefunction of executing a predetermined function in accordance with a codeor instruction in a program, and is a central processing unit (CPU), forexample. Furthermore, the control unit 21 may also be, for example, amicroprocessor, a multiprocessor, an application-specific integratedcircuit (ASIC), a field programmable gate array (FPGA), or the like.Note that, in the first embodiment of the present invention, the controlunit 21 is not limited to these examples.

As shown in FIG. 3, the control unit 21 includes, for example, acomparison unit 22, a generation unit 23, and a notification unit 24.

The comparison unit 22 executes matching between sensor-side metadataand application-side metadata. The comparison unit 22 determines whetheror not there is sensor-side metadata that matches application-sidemetadata. Furthermore, the comparison unit 22 may also determine whetheror not, for example, there is sensor-side metadata that matches at leastpart of information contained in the application-side metadata.Furthermore, the comparison unit 22 may also determine whether or not,for example, there is sensor-side metadata that satisfies apredetermined condition contained in the application-side metadata.

In the first embodiment of the present invention, the comparison unit 22can execute matching based on, for example, static information (staticcomponents) contained in sensor-side metadata and application-sidemetadata. For example, the comparison unit 22 executes matching betweensensor-side metadata and application-side metadata with reference to thesensor-side metadata storage unit 25 and the application-side metadatastorage unit 26.

The comparison unit 22 may also execute, every time application-sidemetadata is received, matching between sensor-side metadata and theapplication-side metadata, for example. Furthermore, the comparison unit22 may also execute matching between sensor-side metadata andapplication-side metadata at a predetermined cycle, for example.Furthermore, the comparison unit 22 may also execute matching betweensensor-side metadata and application-side metadata upon receiving arequest from a data user, for example. Note that the timing at which thecomparison unit 22 executes matching is not limited to these examples,and may be any timing.

If matching executed by the comparison unit 22 is successful, thegeneration unit 23 generates, based on the result of the matching, adata flow control command that includes information relating to a sensorand information relating to an application that uses sensing data. Thegeneration unit 23 generates, based on the matched sensor-side metadata,a data flow control command that includes information relating to thesensor 4 that can provide the sensing data. The generation unit 23 adds,to the data flow control command, an identifier that can identify thesensor 4 and is contained in the matched sensor-side metadata, forexample.

Furthermore, the generation unit 23 generates, based on the matchedapplication-side metadata, a data flow control command that includesinformation relating to the application server 5 that uses the sensingdata. The generation unit 23 adds, to the data flow control command, anidentifier that can identify the application server 5 and is containedin the matched application-side metadata, for example.

Furthermore, the generation unit 23 may also add, to the data flowcontrol command, information relating to data (event data) of thesensing data that changes every moment or every time a measurement ismade, the information being contained in the sensor-side metadata.Furthermore, the generation unit 23 may add, to the data flow controlcommand, an “event condition”, which is a condition that relates toinformation that dynamically changes, and is contained in theapplication-side metadata. Note that the event data is not limited todata of the sensing data that changes every moment or every time ameasurement is made, and may be data that changes every moment or everytime a measurement is made, obtained by another sensor different fromthe sensor that collect the sensing data.

Here, the comparison unit 22, the generation unit 23, and thenotification unit 24 are realized, for example, by a central processingunit, a microprocessor, a processor core, a multiprocessor, anapplication-specific integrated circuit (ASIC), a field programmablegate array (FPGA), or the like.

The notification unit 24 gives the data flow control command generatedby the generation unit 23 to the sensor management device 3 via thecommunication unit 20.

The control device 2 includes the sensor-side metadata storage unit 25.The sensor-side metadata storage unit 25 stores sensor-side metadatareceived via the communication unit 20. The sensor-side metadata storageunit 25 is realized by any of various types of storage media such as ahard disk drive (HDD), a solid state drive (SSD), and a flash memory,for example. Note however that, in the first embodiment of the presentinvention, the sensor-side metadata storage unit 25 is not limited tothese examples.

The control device 2 includes the application-side metadata storage unit26. The application-side metadata storage unit 26 storesapplication-side metadata received via the communication unit 20. Theapplication-side metadata storage unit 26 is realized by any of varioustypes of storage media such as a HDD, a SSD, and a flash memory, forexample. Note however that, in the first embodiment of the presentinvention, the application-side metadata storage unit 26 is not limitedto these examples.

Example of Configuration of Sensor Management Device 3

FIG. 4 is a diagram showing an example of a configuration of the sensormanagement device 3 according to the first embodiment of the presentinvention. As shown in FIG. 4, the sensor management device 3 includes acommunication unit 30, a determination unit 31 and a sensing datastorage unit 34.

The communication unit 30 is a communication interface for connection tothe control device 2, the sensor 4, and the application server 5. Thesensor management device 3 receives a data flow control command from thecontrol device 2 via the communication unit 30.

Furthermore, the sensor management device 3 receives sensing data fromthe sensor 4 via the communication unit 30. For example, the sensormanagement device 3 receives an image captured by a camera, which is asensor 4, via the communication unit 30. Note that the sensor managementdevice 3 may also receive data relating to sensing data from anothersensor 7 attached to the sensor 4 via the communication unit 30. Forexample, the sensor management device 3 may also receive data of a GPS,which is another sensor 7 attached to the camera, via the communicationunit 30.

Furthermore, the sensor management device 3 instructs, via thecommunication unit 30, the sensor 4 to deliver the sensing data to theapplication server 5. Note that the sensor management device 3 may alsotransfer the sensing data received from the sensor 4 to the applicationserver 5, instead of instructing the sensor 4 to deliver it.

The determination unit 31 functions to determine whether or not, of thesensing data received from the sensor 4, data (event data) that changesevery moment or every time a measurement is made satisfies an “eventcondition” contained in the data flow control command. The determinationunit 31 has the function of executing a predetermined function inaccordance with a code or instruction in a program, and is a centralprocessing unit (CPU), for example. Furthermore, the determination unit31 may also be, for example, a microprocessor, a multiprocessor, anASIC, a FPGA, or the like. Note that, in the first embodiment of thepresent invention, the determination unit 31 is not limited to theseexamples.

As shown in FIG. 4, the determination unit 31 includes, for example, adetection unit 32 and a delivery unit 33.

The detection unit 32 detects that, of the sensing data received fromthe sensor 4, data (event data) that changes every moment or every timea measurement is made satisfies an “event condition” contained in thedata flow control command. For example, the detection unit 32 detectsthat an image captured by the camera, which is a sensor 4, satisfies an“event condition” set in the application-side metadata. Furthermore, thedetection unit 32 may also detect that data relating to sensing datasatisfies a predetermined condition of an “event condition”. Forexample, the detection unit 32 may also detect that data of a GPS, whichis another sensor 7 attached to the camera, satisfies an “eventcondition”. Note that the detection unit 32 specifies a sensor 4 basedon information that specifies the sensor 4 contained in the data flowcontrol command, and detects that the sensing data received from thespecified sensor 4 satisfies an “event condition”.

If it is detected by the detection unit 32 that event data contained insensing data satisfies an “event condition”, the delivery unit 33instructs the sensor 4 to deliver the sensing data to the applicationserver 5. For example, if it is detected that an image (event data)captured by a camera, which is a sensor 4, satisfies an “eventcondition”, the delivery unit 33 instructs the camera to deliver thisimage. Furthermore, if it is detected by the detection unit 32 that datarelating to sensing data satisfies an “event condition”, the deliveryunit 33 instructs the sensor 4 to deliver this sensing data to theapplication server 5. For example, if it is detected that data (eventdata) of a GPS, which is another sensor 7 attached to the camera,satisfies an “event condition”, the delivery unit 33 instructs thecamera to deliver the image.

Note that, when sensing data is received from a sensor 4, the deliveryunit 33 may also deliver the received sensing data to the applicationserver 5, instead of instructing the sensor 4 to deliver the sensingdata.

The sensing data storage unit 34 stores sensing data received from thesensor 4. Note that the sensing data storage unit 34 may temporarilystore, for example, sensing data received from the sensor 4. Note thatthe sensing data storage unit 34 is realized by any of various types ofstorage media such as a HDD, a SSD, a flash memory, for example. Notehowever that, in the first embodiment of the present invention, thesensing data storage unit 34 is not limited to these examples.

Example of Operation

FIG. 5 is a flowchart showing an example of an operation of the controldevice 2 according to the first embodiment of the present invention.

The communication unit 20 of the control device 2 receives sensor-sidemetadata, which is information relating to sensing data, from a dataprovider (step S101), and stores the received sensor-side metadata inthe sensor-side metadata storage unit 25 (step S102). Note that thecommunication unit 20 receives a plurality of pieces of sensor-sidemetadata from a plurality of data providers, and every time a piece ofsensor-side metadata is received, the communication unit 20 stores thereceived piece of sensor-side metadata in the sensor-side metadatastorage unit 25.

Furthermore, the communication unit 20 receives, from a data user,application-side metadata that indicates content of sensing data desiredto be used by the data user (step S103), and stores the receivedapplication-side metadata in the application-side metadata storage unit26 (step S104).

Note that the processes in steps S101 and S102 and the processes insteps S103 and S104 may also be executed in reverse order, such that theprocesses in steps S103 and S104 are first executed, and then theprocesses in steps S101 and S102 are executed.

The comparison unit 22 executes matching between the sensor-sidemetadata and the application-side metadata (step S105). The comparisonunit 22 determines whether or not, for example, static informationcontained in the application-side metadata matches static informationcontained in the application-side metadata.

If the matching executed by the comparison unit 22 is successful (YES instep S105), the generation unit 23 generates, based on a result of thematching, a data flow control command that includes information relatingto the sensor 4 and information relating to the application server 5that uses the sensing data (step S106). Note that the generation unit 23adds, to the data flow control command, information relating to data(event data) of the sensing data that changes every moment or every timea measurement is made, and is contained in the sensor-side metadata.Furthermore, the generation unit 23 adds, to the data flow controlcommand, an “event condition”, which is a condition relating toinformation that changes dynamically and is contained in theapplication-side metadata. On the other hand, if the matching executedby the comparison unit 22 is not successful (NO in step S105), thegeneration unit 23 ends the procedure.

The notification unit 24 gives the data flow control command generatedby the generation unit 23 to the sensor management device 3 via thecommunication unit 20 (step S107).

FIG. 6 is a flowchart showing an example of an operation of the sensormanagement device 3 according to the first embodiment of the presentinvention.

The communication unit 30 of the sensor management device 3 receives thedata flow control command from the control device 2 (step S201).

The detection unit 32 specifies a sensor 4 based on information thatspecifies the sensor 4 contained in the received data flow (step S202).The detection unit 32 determines whether or not the sensing datareceived from the specified sensor 4 or the data received from anothersensor 7 attached to the sensor 4 satisfies the “event condition”contained in the data flow control command (step S203).

If it is determined by the detection unit 32 that the “event condition”is satisfied (YES in step S203), the delivery unit 33 delivers thesensing data to the application server 5 (step S204). Note that theapplication server 5 is specified through information that specifies anapplication server 5 that is contained in the data flow control command.On the other hand, if it is determined by the detection unit 32 that thepredetermined condition is not satisfied (NO in step S203), the deliveryunit 33 returns to step S203.

As described above, in the first embodiment of the present invention,the control device 2 executes, in advance, matching based on staticinformation contained in sensor-side metadata and application-sidemetadata, and then the sensor management device 3 determines whether ornot “event data” satisfies an “event condition”, and judges whether ornot the sensing data is to be delivered. Accordingly, the processingload required for the matching can be dispersed between the controldevice 2 and the sensor management device 3. Accordingly, the controldevice 2 does not need to execute matching using “event data” thatchanges dynamically, and thus it is possible to suppress an increase inthe processing load. On the other hand, because a sensor managementdevice 3 is provided for each sensor (or an attribute of the sensor), itis less likely that the sensor management device 3 needs to executematching using “event data” that changes dynamically for a plurality ofpairs, and thus the processing load thereof is less likely todrastically increase. Accordingly, in the first embodiment of thepresent invention, a drastic increase in the processing load on thecontrol device 2 can be prevented, and even if “event data”, whichchanges dynamically, is used as a condition for matching, sensing datafrom a data provider can be delivered to a data user, thus facilitatinguse of the sensing data.

WORKING EXAMPLE 1

A working example 1 is a working example in which the data providingsystem 1 is applied to delivery of an image captured by an on-boardcamera, which is a sensor 4.

FIG. 7 is a diagram showing an example of a configuration of the dataproviding system 1 according to the working example 1. As shown in FIG.7, in the working example 1, the data providing system 1 includes mobileobjects 8 each provided with a sensor 4 and another sensor 7.

The mobile objects 8 are, for example, moving objects such asautomobiles, buses, motortrucks, or electric trains. Note that themobile objects 8 are not limited to these examples, and may be any typeof object as long as they are moving objects. Note that the followingexample will be described, taking a case where the mobile objects 8 arebuses as an example.

As shown in FIG. 7, each mobile object 8 is provided with a sensor 4,another sensor 7, and a network adapter 80. The sensor 4 is, forexample, a camera that can capture a view outside of the mobile object8. The sensor 4 is, for example, a camera that can capture a viewforward of and outside of the mobile object 8. Note that the directionin which the sensor 4 can capture a view outside of the mobile object 8is not limited to the forward direction, and may be any direction out offorward, backward, leftward, and rightward directions. Furthermore, thesensor 4 may be able to capture a view outside of the mobile object 8 asa still image or as a moving image (video). Furthermore, the mobileobject 8 may also be provided with a plurality of sensors 4.

The sensor 4 captures a view outside of the mobile object 8 at apredetermined timing. The predetermined timing may be, for example, apredetermined cycle, and may be any cycle such as a one second intervalor a one minute interval. Furthermore, the predetermined timing may be,for example, a timing at which the mobile object 8 makes a turn at anintersection, a timing at which the mobile object 8 stops or startsmoving, a timing at which the mobile object 8 accelerates ordecelerates, or another timing. Furthermore, the predetermined timingmay be a timing at which the time is at a predetermined time, a timingat which a request for image capture is made, or another timing.

The other sensor 7 is a sensor that collects information relating to themobile object 8 at a predetermined timing. The other sensor 7 may alsobe any device such as, for example, a GPS that can measure the currentlocation of the mobile object 8, or an acceleration sensor that candetect the speed or acceleration of the mobile object 8. Furthermore, ifthe mobile object 8 is a bus or an electric train, the other sensor 7may also be a sensor that can detect the boarding situation or a vacantseat situation. The other sensor 7 is not limited to these examples, andmay be any sensor as long as it can collect information relating to themobile object 8.

The other sensor 7 collects information relating to the mobile object 8at a predetermined timing. Similar to the case of the sensor 4, thepredetermined timing may be any cycle such as a predetermined cycle (aone second interval or a one minute interval), a timing at which apredetermined time has come, or a timing at which a request for imagecapture is made, for example.

The network adapter 80 is a communication interface that can transmitsensing data collected by the sensor 4 or data collected by the othersensor 7. The sensor 4 or the other sensor 7 transmits, via the networkadapter 80, the sensing data or the collected data to the sensormanagement device 3 or the application server 5.

As shown in FIG. 7, in the working example 1, there may be a pluralityof mobile objects 8. Each of the plurality of mobile objects 8 canprovide sensing data to be used by the application server 5.

FIG. 8 is a diagram showing an example of a configuration of sensor-sidemetadata that is received by the control device 2 according to theworking example 1. As shown in FIG. 8, the sensor-side metadata includesinformation relating to sensing data that can be provided by at leastone of the plurality of mobile objects 8. The sensor-side metadatapartially contains dynamic information, in addition to staticinformation. The dynamic information is, for example, a measurementitem.

As shown in FIG. 8, the sensor-side metadata contains, as the staticinformation, information indicating a category, a data delivery entity,or the like, for example. On the other hand, the sensor-side metadatacontains, as an event condition, a measurement item, for example. Theevent condition is, for example, information that changes overtime orinformation that changes every time a measurement is made, and examplesthereof include a measurement item, a measurement location, and ameasurement time.

The sensor-side metadata contains a category of the sensing data. Acategory of the sensing data is, for example, “sightseeing”, “mobiletype”, or the like. The information relating to a category is staticinformation (static component).

Furthermore, the sensor-side metadata contains information relating to adata delivery entity, for example. The information relating to a datadelivery entity is information relating to an entity that provides thesensing data. If a mobile object 8 provided with a sensor 4 is a bus,the information relating to a data delivery entity is a bus company name“bus business operator A” or the like. The information relating to adata delivery entity is static information (static component).

Furthermore, the sensor-side metadata contains, for example, ameasurement object name, and is information indicating the name of anobject for which sensing data is measured. If the mobile object 8provided with the sensor 4 is a bus, the measurement object name is, forexample, an area or a bus route in which the bus service is provided, avehicle number with which the bus provided with the sensor 4 can beidentified, or the like. In the example of FIG. 8, the measurementobject name includes “area B, bus route C, bus numbers X, Y, Z”. Theinformation relating to a measurement object name is static information(a static component).

Furthermore, the sensor-side metadata contains, for example, ameasurement item, which indicates content of sensing data measured bythe sensor 4. The measurement item includes, for example, a “still viewimage”, “real-time positional coordinates of the bus”, “time”, and thelike. The measurement item is information that changes over time orinformation that changes every time a measurement is made, and is thusdynamic information. For example, “real-time positional coordinates ofthe bus” is an event condition because the positional coordinates changeover time, namely, from moment to moment. Furthermore, a still viewimage captured from a moving bus changes every time an image iscaptured, and thus is an event condition.

Furthermore, the sensor-side metadata contains, for example, a datausage range, and contains information relating to a range in which useof sensing data is conceivable. The data usage range includes, forexample, “non-commercial use”, “virtual sightseeing”, “urban area staterecognition”, and the like. The information relating to a data usagerange is static information (a static component).

Furthermore, the sensor-side metadata contains an item “what can behandled as dynamic metadata”, which indicates information usable asdynamic metadata. The information contained in the item “what can behandled as dynamic metadata” can be used as dynamic metadata. Theinformation set as “what can be handled as dynamic metadata” is, forexample, data of sensing data that changes every moment or every time ameasurement is made. In the example of FIG. 8, the information set aswhat can be handled as dynamic metadata is “real-time positionalcoordinates of the bus” and “time”.

Furthermore, the sensor-side metadata may contain, for example, detailedinformation of an event condition. In the example of FIG. 8, detailedinformation of an event condition includes “mobile type” for ameasurement location, and a “detailed operation schedule” of the bus.Information relating to a measurement location is information relatingto a location at which the sensing data is measured, and is informationindicating whether it is fixed-type information or mobile-typeinformation, or information relating to a specific measurement location.Furthermore, detailed information of a dynamic component includes “aninterval of one second” for measurement time. The information relatingto measurement time is information relating to time or a time period atwhich or for which the sensing data is measured.

FIG. 9 is a diagram showing an example of a configuration ofapplication-side metadata that is received by the control device 2 inthe working example 1. As shown in FIG. 9, the application-side metadataincludes information relating to sensing data desired to be used by theapplication server 5. As shown in FIG. 9, the application-side metadatacontains static information and dynamic information. The staticinformation (static component) is, for example, information indicating acategory, a data delivery entity, and the like. The event condition is,for example, information that changes over time, and includes ameasurement location and a measurement time, for example.

The application-side metadata contains a category of data desired to beused, such as “sightseeing” and “mobile type”, for example. Furthermore,the application-side metadata contains, for example, informationrelating to a data delivery entity, and is, for example, informationrelating to an entity that provides sensing data, and the like, and is“bus business operator A” in the example of FIG. 9. Furthermore, theapplication-side metadata includes a measurement object name, which isinformation indicating the name of a measurer (measurement object) ofsensing data desired to be used. The measurement object name is, forexample, “area B, bus route C, bus numbers X, Y, Z” and the like.Furthermore, the application-side metadata contains a data usage range,and the data usage range is, for example, information relating to a“usage” of the sensing data. In the example of FIG. 9, the data usagerange is, for example, “virtual sightseeing”. These pieces ofinformation are static information (static components).

Note that, in the application-side metadata, if there is no need tospecify, for example, a category, a data delivery entity, a measurementobject name, and a data usage range of the sensing data, these items maybe blank or may include information indicating that no specification isneeded (such as XXX).

The application-side metadata contains, for example, a measurement item,and can designate an attribute, a property, and a characteristic ofsensing data desired to be used. The measurement item is, for example, a“still view image”, a “moving image”, or the like. By designating theattribute of sensing data as the measurement item of application-sidemetadata, the data user or the application server 5 can specify theattribute of sensing data that the data user or the application serversdesires to use. Furthermore, these pieces of information are pieces ofinformation that change every moment or every time a measurement ismade, and are event conditions.

The application-side metadata contains, for example, as event conditiondetails, information relating to a state of the measurement location. Bydesignating a state of the measurement location, the data user or theapplication server 5 can designate the measurement location of thesensing data that the data user or the application server 5 desires touse. In the example of FIG. 9, as a condition of the measurementlocation, “positional coordinates within a radius of 20 m from Nijo-joCastle” is input, for example.

Furthermore, the application-side metadata contains, as the eventcondition details, information relating to measurement time, forexample. By designating a condition of the measurement time, the datauser or the application server 5 can designate the measurement time ofthe sensing data that the data user or the application server 5 desiresto use. In the example of FIG. 9, as a condition of the measurementtime, “first passing timing after 9:45” is input, for example.

The control device 2 receives, from a data provider, sensor-sidemetadata as exemplified in FIG. 8, and stores the received sensor-sidemetadata in the sensor-side metadata storage unit 25. Furthermore, thecontrol device 2 receives, from the data user or the application server5, application-side metadata as exemplified in FIG. 9, and stores thereceived application-side metadata in the application-side metadatastorage unit 26.

The comparison unit 22 of the control device 2 executes matching betweenthe sensor-side metadata and the application-side metadata. Thecomparison unit 22 searches for sensor-side metadata that matches itemsof static information (static components) of the application-sidemetadata with reference to the sensor-side metadata storage unit 25. Thecomparison unit 22 searches for sensor-side metadata that matches itemsof static information (static components) of the application-sidemetadata, based on the application-side metadata exemplified in FIG. 9,for example. Then, the comparison unit 22 specifies, as a result of thesearch based on the application-side metadata exemplified in FIG. 9,sensor-side metadata exemplified in FIG. 8.

Note that the comparison unit 22 may also search for sensor-sidemetadata that matches at least some of application-side metadata.

If the matching executed by the comparison unit 22 is successful, thegeneration unit 23 generates a “data flow control command” that includesinformation relating to the sensor 4 that can be specified based on the“measurement object name”, which is an item of the sensor-side metadata,and information relating to the application server 5 from which theapplication-side metadata was transmitted. Furthermore, the generationunit 23 adds, to the data flow control command, information that relatesto data (event data) of the sensing data that changes every moment orevery time a measurement is made, and is contained in the sensor-sidemetadata. Furthermore, the generation unit 23 adds, to the data flowcontrol command, an “event condition” that is a condition relating toinformation that dynamically changes, and is contained in theapplication-side metadata. The “event condition” is an event conditionof the application-side metadata, and includes, in the example of FIG.9, a “condition of a measurement location” and a condition of“measurement time”. Specifically, the generation unit 23 adds, to thedata flow control command, information indicating “positionalcoordinates within a radius of 20 m from Nijo-jo Castle” serving as acondition of a measurement location and “first passing timing after9:45” serving as a condition of measurement time.

The notification unit 24 gives the data flow control command generatedby the generation unit 23 to the sensor management device 3 via thecommunication unit 20.

The detection unit 32 of the sensor management device 3 determineswhether or not sensing data received from a sensor 4 satisfies the“event condition” included in the data flow control command receivedfrom the control device 2. The detection unit 32 determines, forexample, whether or not sensing data received from at least one of thesensors 4 included in a plurality of mobile objects 8 satisfies the“event condition”. Furthermore, the detection unit 32 may also determinewhether or not data received from another sensor 7 satisfies the “eventcondition”.

For example, the detection unit 32 determines whether or not a stillview image received from a camera, which is a sensor 4 included in eachof the plurality of mobile objects 8, satisfies both of the conditions“positional coordinates within a radius of 20 m from Nijo-jo Castle” and“first passing timing after 9:45”. For example, based on GPS datareceived from another sensor 7 included in a mobile object 8 togetherwith a still view image received from a camera, which is a sensor 4, thedetection unit 32 may also determine that the measurement location atwhich the still view image was captured satisfies both the conditions“positional coordinates within a radius of 20 m from Nijo-jo Castle” and“first passing timing after 9:45”. Note that a GPS can collect, forexample, information in which an identifier that can identify a mobileobject 8, information relating to the current position (positionalcoordinates) of the mobile object 8, and information relating to thecurrent time are associated with each other, and can transmit theinformation as another type of data to the sensor management device 3.Accordingly, the detection unit 32 can determine, based on the datareceived from the GPS, which is the other sensor 7, whether or not thesensing data received from the sensor 4 satisfies the “event condition”.

The detection unit 32 performs processing to determine whether or notsensing data received from a sensor 4 satisfies the “event condition”until it receives the sensing data that satisfies the “event condition”included in the data flow control command.

If it is detected by the detection unit 32 that sensing data satisfiesthe “event condition”, the delivery unit 33 instructs the sensor 4 todeliver the sensing data to the application server 5. If, for example,the still view image received from the sensor 4 is a still view imagethat satisfies the conditions “positional coordinates within a radius of20 m from Nijo-jo Castle” and “first passing timing after 9:45”, thedelivery unit 33 instructs the sensor 4 to deliver the still view imageto the application server 5.

Note that the delivery unit 33 may also deliver the still view imagereceived from the sensor 4 to the application server 5, instead ofinstructing the sensor 4 to deliver it.

As described above, according to the working example 1 of the firstembodiment of the present invention, in the data providing system 1 fordelivering an image from an on-board camera, which is a sensor 4, it ispossible to reduce the processing load on the control device 2 requiredfor performing matching between information relating to the image fromthe on-board camera, which is a sensor 4, and information relating to anapplication that uses sensing data.

WORKING EXAMPLE 2

A working example 2 is a working example in which the data providingsystem 1 is applied to various sensors 4.

FIG. 10 illustrate examples of configurations of sensor-side metadataand application-side metadata according to the working example 2. Thecontrol device 2 receives, for example, sensor-side metadata exemplifiedin FIG. 10(a) from a data provider. Note that the examples of FIG. 10are examples of configurations of sensor-side metadata andapplication-side metadata in a case where a data user or an applicationserver 5 examines the highest temperatures in the summer across thecountry. In this case, the sensors 4 are, for example, temperaturesensors.

As shown in FIG. 10(a), the sensor-side metadata contains “weather” as acategory, “Meteorological Agency” as a data delivery entity, and “sensoroo in oo city in oo prefecture” as a measurement object name.Furthermore, the sensor-side metadata contains “oo city in ooprefecture” as a measurement location, and “research” as a data usagerange. These pieces of information are static information (staticcomponents).

Furthermore, the sensor-side metadata contains “temperature” and “time”as measurement items. These pieces of information are event conditions.Furthermore, the sensor-side metadata contains “temperature” and “time”as information set as data that can be handled as dynamic metadata.Also, the sensor-side metadata contains, as an event condition detail,“interval of one minute” regarding the measurement time.

On the other hand, the control device 2 receives, from the data user orthe application server 5, application-side metadata exemplified in FIG.10(b). The application-side metadata contains, as static information(static components), “weather” serving as a category, “MeteorologicalAgency” serving as a data delivery entity, “sensor oo in oo city in ooprefecture” serving as a measurement object name, “oo city in ooprefecture” serving as a measurement location, and “global warmingresearch” serving as a data usage range. Furthermore, theapplication-side metadata contains, as event conditions, “temperature”and “time” serving as measurement items. Also, the application-sidemetadata contains, as event condition details, “temperature of 30degrees or higher”, “temperature”, and “time” regarding measurementconditions.

The comparison unit 22 of the control device 2 executes matching of thesensor-side metadata, based on the static information included in theapplication-side metadata.

Then, the generation unit 23 adds, to a data flow control command, thedynamic information of the application-side metadata “when thetemperature is 30 degrees or higher”, as an “event condition”. Note thatthe generation unit 23 adds, to the data flow control command, anidentifier that can identify “sensor oo in oo city in oo prefecture” asinformation that specifies the sensor 4, and an identifier that canspecify the application server 5.

The detection unit 32 of the sensor management device 3 monitors, basedon the data flow control command received from the control device 2,information relating to the temperature, which is sensing data, theinformation being received from the “sensor oo in oo city in ooprefecture”, which is the specified sensor 4. If the informationrelating to the temperature received from the “sensor oo in oo city inoo prefecture” satisfies the “event condition”, that is, “when thetemperature is 30 degrees or higher”, the detection unit 32 instructsthe delivery unit 33 to deliver the information relating to thetemperature to the application server 5.

The delivery unit 33 instructs the “sensor oo in oo city in ooprefecture”, which is a sensor 4, to deliver the information relating tothe temperature, which is sensing data, to the application server 5.Note that the delivery unit 33 may also deliver the sensing datareceived from the sensor 4 to the application server 5, instead ofinstructing the sensor 4 to deliver it.

Furthermore, FIG. 11 illustrate other examples of the configurations ofsensor-side metadata and application-side metadata, according to theworking example 2. The control device 2 receives, for example,sensor-side metadata exemplified in FIG. 11(a) from a data provider.Note that the examples of FIG. 11 are examples of configurations ofsensor-side metadata and application-side metadata in a case where adata user or an application server 5 is investing the production ofsolar power. In this case, the sensors 4 are, for example, electricvoltage/current sensors.

As shown in FIG. 11(a), the sensor-side metadata contains “electricpower” as a category, “power generation business operator B of solarcells” as a data delivery entity, “solar cell ΔΔ in ΔΔ city in ΔΔprefecture” as a measurement object name, “ΔΔ city in ΔΔ prefecture” asa measurement location, and “research” as a data usage range, and thesepieces of information are static information. Furthermore, thesensor-side metadata contains “voltage” and “time” as measurement items,and these pieces of information are event conditions. Furthermore, thesensor-side metadata contains “electric power” and “time” as informationset as data that can be handled as dynamic metadata. Furthermore,“interval of one second” regarding the measurement time is contained asan event condition detail.

On the other hand, the control device 2 receives, from the data user orthe application server 5, application-side metadata exemplified in FIG.11(b). The application-side metadata contains “electric power” as acategory, “power generation business operator B of solar cells” as adata delivery entity, “solar cell ΔΔ in ΔΔ city in ΔΔ prefecture” as ameasurement object name, “ΔΔ city in ΔΔ prefecture” as a measurementlocation, and “solar cell research” as a data usage range, and thesepieces of information are static information. Furthermore, theapplication-side metadata contains “electric power” and “time” asmeasurement items, and these pieces of information are event conditions.Also, the application-side metadata contains, as an event conditiondetail, “when the production of electricity is 1 W or greater”,“electric power”, and “time” regarding the measurement conditions.

The comparison unit 22 of the control device 2 executes matching of thesensor-side metadata, based on static information contained in theapplication-side metadata.

Then, the generation unit 23 adds, to a data flow control command, thedynamic information of the application-side metadata “when theproduction of electricity is 1 W or greater” as an “event condition”.Note that the generation unit 23 adds, to the data flow control command,an identifier that can identify “solar cell ΔΔ in ΔΔ city in ΔΔprefecture” as information that specifies the sensor 4, and anidentifier that can specify the application server 5.

The detection unit 32 of the sensor management device 3 monitors, basedon the data flow control command received from the control device 2,information relating to the temperature, which is sensing data, theinformation being received from the “solar cell ΔΔ in ΔΔ city in ΔΔprefecture”, which is the specified sensor 4. If the informationrelating to the electric power received from the “solar cell ΔΔ in ΔΔcity in ΔΔ prefecture” satisfies the “event condition”, that is, “whenthe production of electricity is 1 W or greater”, the detection unit 32instructs the delivery unit 33 to deliver the information relating tothe temperature to the application server 5.

The delivery unit 33 instructs the “solar cell ΔΔ in ΔΔ city in ΔΔprefecture”, which is a sensor 4, to deliver the information relating toelectric power, which is sensing data, to the application server 5. Notethat the delivery unit 33 may also deliver the sensing data receivedfrom the sensor 4 to the application server 5, instead of instructingthe sensor 4 to deliver it.

Moreover, FIG. 12 illustrate yet other examples of the configurations ofsensor-side metadata and application-side metadata, according to theworking example 2. The control device 2 receives, for example,sensor-side metadata exemplified in FIG. 12(a) from a data provider.Note that the examples of FIG. 12 are examples of configurations ofsensor-side metadata and application-side metadata in a case where adata user or an application server 5 is investigating whether or not asuspicious individual is in the city. In this case, the sensors 4 are,for example, security cameras. As shown in FIG. 12(a), the sensor-sidemetadata contains “crime prevention” as a category, “owner C of asecurity camera in a park” as a data delivery entity, “camera

in the park in

town in

city in

prefecture” as a measurement object name, “

town in

city in

prefecture” as a measurement location, and “crime prevention” as a datausage range, and these pieces of information are static information(static components). Furthermore, the sensor-side metadata contains“image” and “time” as measurement items, and these pieces of informationare event conditions. Furthermore, the sensor-side metadata contains“image” and “time” as information set as data that can be handled asdynamic metadata. Also, the sensor-side metadata contains, as an eventcondition detail, “interval of 0.1 seconds” regarding the measurementtime.

On the other hand, the control device 2 receives, from a data user or anapplication server 5, application-side metadata exemplified in FIG.12(b). The application-side metadata contains, as static information(static components), “crime prevention” serving as a category, “owner Cof a security camera in a park” serving as a data delivery entity,“camera

in the park in

town in

city in

prefecture” serving as a measurement object name, “

town in

city in

prefecture” serving as a measurement location, and “crime prevention”serving as a data usage range. Furthermore, the application-sidemetadata contains, as event conditions, “image” and “time” serving asmeasurement items. Also, the application-side metadata contains, asevent condition details, “when a suspicious individual appears on animage captured by the security camera”, “image”, and “time” regardingmeasurement conditions.

The comparison unit 22 of the control device 2 executes matching of thesensor-side metadata, based on the static information contained in theapplication-side metadata.

Then, the generation unit 23 adds, to a data flow control command, thedynamic information of the application-side metadata “when a suspiciousindividual appears on an image captured by the security camera” as an“event condition”. Note that the generation unit 23 adds, to the dataflow control command, an identifier that can identify “camera

in the park in

town in

city in

prefecture” as information that specifies the sensor 4, and anidentifier that can specify the application server 5.

The detection unit 32 of the sensor management device 3 monitors, basedon the data flow control command received from the control device 2,information relating to an image, which is sensing data, the informationbeing received from the “camera

in the park in

town in

city in

prefecture”, which is the specified sensor 4. If the image received fromthe “camera

in the park in

town in

city in

prefecture” includes a “captured suspicious individual”, which is an“event condition”, the detection unit 32 instructs the delivery unit 33to deliver the information relating to the image to the applicationserver 5. Note that the detection unit 32 can use various existingmethods to detect whether or not the image includes a capturedsuspicious individual.

The delivery unit 33 instructs the “camera

in the park in

town in

city in

prefecture”, which is a sensor 4, to deliver the image, which is sensingdata, to the application server 5. Note that a delivery unit 33 may alsodeliver the sensing data received from the sensor 4 to the applicationserver 5, instead of instructing the sensor 4 to deliver it.

As described above, in the working example 2 of the first embodiment ofthe present invention, the data providing system 1 is applicable tovarious sensors 4.

Second Embodiment

A second embodiment of the present invention is an embodiment in which,when a plurality of entities can provide sensor-side metadata, one ofthe plurality of data providers (for example, the plurality of entities)provides sensing data to an application server. Note that the secondembodiment of the present invention is also applicable to the firstembodiment.

FIG. 13 is a diagram showing an example of a configuration of the dataproviding system 1 according to the second embodiment of the presentinvention. As shown in FIG. 13, in the second embodiment of the presentinvention, the data providing system 1 includes a plurality of mobileobjects 8 each provided with a sensor 4 and another sensor 7. The dataproviding system 1 further includes a plurality of sensor managementdevices 3 that manage at least one sensor 4 and another sensor 7.

Each of the plurality of sensor management devices 3 is provided for,for example, a data provider that can provide sensing data, and managesthe sensor 4 and the other sensor 7 of this data provider. For example,in FIG. 13, a sensor management device 3A manages a sensor 4A andanother sensor 7A that are included in a mobile object 8A belonging to adata provider A. Furthermore, a sensor management device 3B manages asensor 4B and another sensor 713 that are included in a mobile object 8Bbelonging to a data provider B. Furthermore, a sensor management device3C manages a sensor 4C and another sensor 7C that are included in amobile object 8C belonging to a data provider.

Note that each of the sensor management devices 3 can manage a pluralityof sensors 4 and a plurality of other sensors 7. For example, the sensormanagement device 3A can manage a plurality of sensors 4A and aplurality of other sensors 7A.

FIG. 14 is a diagram showing an example of a configuration of thecontrol device 2 according to the second embodiment of the presentinvention. As shown in FIG. 14, the control device 2 includes a contractstate management unit 27.

The control device 2 receives sensor-side metadata from a plurality ofdata providers, for example. FIG. 15 illustrate examples ofconfigurations of sensor-side metadata that are received from the dataproviders A to C, for example. As shown in FIG. 15, the sensor-sidemetadata received from the data providers A to C differ from each otherin “data delivery entity” and “measurement object name” for example, andcontain the same information regarding the remaining items.

The control device 2 receives, from a data user or an application server5, application-side metadata exemplified in FIG. 9.

The comparison unit 22 of the control device 2 searches for sensor-sidemetadata that matches the items of the application-side metadata, withreference to the sensor-side metadata storage unit 25. As a result, thecomparison unit 22 specifies the three pieces of sensor-side metadatashown in FIG. 15.

The generation unit 23 generates, for each of the pieces of sensor-sidemetadata specified by the comparison unit 22, a “data flow controlcommand” that includes information relating to the sensor 4 andinformation relating to the application server 5. If, for example, threepieces of sensor-side metadata are specified by the comparison unit 22,the generation unit 23 generates three data flow control commands.Furthermore, the generation unit 23 adds, to each of the generated dataflow control commands, an “event condition”. For example, the generationunit 23 adds, to each of the generated data flow control commands,information that indicates “positional coordinates within a radius of 20m from Nijo-jo Castle” and “first passing timing after 9:45”, serving as“event conditions”.

The notification unit 24 respectively gives the data flow controlcommands generated by the generation unit 23 to the plurality of sensormanagement devices 3 via the communication unit 20.

The contract state management unit 27 manages the plurality of sensormanagement devices 3 to which the data flow control commands wererespectively given by the notification unit 24. For each request of useof data (that is, application-side metadata), the contract statemanagement unit 27 stores the plurality of sensor management devices 3that were instructed to deliver sensing data based on the request ofuse. The contract state management unit 27 stores, for one piece ofapplication-side metadata, the sensor management devices 3 to which theinstructions to deliver sensing data were given. In the example of FIG.14, the contract state management unit 27 of the control device 2stores, for each piece of application-side metadata, a plurality ofsensor management devices 3 to which the instructions to deliver sensingdata were given, in association with each other.

Furthermore, when any of the plurality of sensor management devices 3has delivered the sensing data to the application server 5, the contractstate management unit 27 notifies the other sensor management devices 3of cancellation of the instruction to deliver the sensing data. Forexample, when the sensor management device 3A, out of the plurality ofsensor management devices 3A to 3C, has delivered the sensing data tothe application server 5, the contract state management unit 27 notifiesthe other sensor management devices 3B and 3C of cancellation of theinstruction to deliver the sensing data.

Each of the plurality of sensor management devices 3 determines whetheror not sensing data received from a sensor 4 satisfies a predeterminedcondition included in the data flow control command received from thecontrol device 2. The detection unit 32 of each sensor management device3 determines, for example, whether or not sensing data received from thesensor 4 included in a mobile object 8 satisfies a predeterminedcondition. Furthermore, the detection unit 32 may also determine whetheror not data received from another sensor 7 satisfies the predeterminedcondition.

For example, a detection unit 32A of the sensor management device 3A inFIG. 13 determines that a still view image received from the camera thatis a sensor 4 included in a mobile object 8 satisfies the conditions“positional coordinates within a radius of 20 m from Nijo-jo Castle” and“first passing timing after 9:45”. In this case, if it is detected bythe detection unit 32A that the sensing data satisfies the predeterminedconditions, a delivery unit 33A of the sensor management device 3Ainstructs the sensor 4A to deliver the sensing data to the applicationserver 5.

Furthermore, the delivery unit 33A of the sensor management device 3Anotifies the control device 2 of the delivery of the sensing data to theapplication server 5.

When the control device 2 is notified of delivery of sensing data fromone of the plurality of sensor management devices 3, the contract statemanagement unit 27 of the control device 2 notifies the remaining sensormanagement devices 3 of cancellation of the instruction to deliversensing data to the application server 5. In the example of FIG. 14, ifthe control device 2 is notified of delivery of sensing data from thesensor management device 3A, the contract state management unit 27notifies the other sensor management devices 3B and 3C of cancellationof the instruction to deliver sensing data to the application server 5.

Upon being notified by the control device 2 of cancellation of theinstruction to deliver sensing data, the remaining sensor managementdevices 3B and 3C cancel delivery of sensing data to the applicationserver 5. Accordingly, the application server 5 receives sensing datafrom the sensor 4 that belongs to the one data provider and not from theother sensor 7, and thus sensing data having the same content can beprevented from being redundantly received.

FIG. 16 is a sequence diagram showing an example of an operation of thedata providing system 1 according to the second embodiment of thepresent invention.

The control device 2 receives sensor-side metadata from a plurality ofdata providers (step S301). The control device 2 receivesapplication-side metadata from a data user or an application server 5(step S302).

The control device 2 searches for sensor-side metadata that matchesitems of static information of the application-side metadata, withreference to the sensor-side metadata storage unit 25 (step S303). Then,the control device 2 generates, for each of the specified plurality ofsensor-side metadata, a data flow control command (step S304). Then, thecontrol device 2 respectively gives the generated data flow controlcommands to a plurality of sensor management devices 3 (step S305). Inthe example of FIG. 16, the control device 2 transmits the data flowcontrol commands to the sensor management devices 3A to 3C.

For example, the sensor 4A or the other sensor 7A attached to thissensor 4A transmits sensing data or another piece of data to the sensormanagement device 3A (step S306).

The sensor management device 3A detects that, for example, the sensingdata received from the sensor 4A satisfies a predetermined conditionincluded in the data flow control command received from the controldevice 2 (step S307). The sensor management device 3A requests thesensor 4A to deliver the sensing data to the application server 5 (stepS308).

The sensor 4A delivers the sensing data to the application server 5 inaccordance with the request from the sensor management device 3A (stepS309).

Upon requesting the sensor 4A to deliver the sensing data, the sensormanagement device 3A notifies the control device 2 of the delivery ofthe sensing data (step S310).

Upon being notified by the sensor management device 3A of the deliveryof the sensing data, the control device 2 notifies the remaining sensormanagement devices 3B and 3C of cancellation of the instruction todeliver sensing data to the application server 5 (step S311). Upon beingnotified by the control device 2 of cancellation of the instruction todeliver sensing data, the remaining sensor management devices 3B and 3Ccancel to deliver the sensing data to the application server 5.

As described above, in the second embodiment of the present invention,when at least one of a plurality of sensor management devices 3 hasdelivered sensing data, the control device 2 notifies the remainingsensor management device 3 of cancellation of delivery of sensing data.Then, upon being notified by the control device 2 of cancellation of theinstruction to deliver sensing data, the other sensor management device3 cancels the delivery of sensing data to the application server 5.Therefore, since the application server 5 receives sensing data from asensor 4 and not from another sensor 7, the sensing data having the samecontent can be prevented from being redundantly received. In this way,in the second embodiment of the present invention, when a plurality ofentities can provide sensor-side metadata, one of the plurality of dataproviders (for example, the plurality of entities) can provide sensingdata to the application server.

The present invention has been described with reference to the drawingsand the working examples, but it should be noted that a person skilledin the art can readily make various modifications and corrections basedon the present disclosure. Accordingly, note that these modificationsand corrections are included in the scope of the present invention. Forexample, functions and the like included in means, steps, and the likecan be rearranged so that they do not logically contradict each other,and a plurality of means, steps, and the like may also be combined intoone or divided. Moreover, configurations shown in the above-describedembodiments may also be combined suitably with each other.

The present invention may also be formulated in the following.

Appendix 1

A control device comprising:

a memory in which a first acquiring unit configured to acquiresensor-side metadata, a second acquiring unit configured to acquireapplication-side metadata, a comparison unit configured to extract asensor that can provide sensing data, and an instruction unit configuredto transmit a data flow control command are stored; and

a hardware processor connected to the memory,

wherein the hardware processor is configured to:

-   -   acquire the sensor-side metadata, which is information relating        to a sensor that can output sensing data;    -   acquire the application-side metadata, which is information        relating to an application that uses the sensing data;    -   execute matching between the sensor-side metadata and the        application-side metadata to extract a sensor that can provide        sensing data that meets a request of the application; and    -   transmit, to a sensor management device that manages the sensor,        a data flow control command that includes information that can        specify the sensor extracted by the comparison unit, and the        application; and

wherein the sensor-side metadata contains information that designatespart of the metadata as being able to be handled as dynamic data,

the application-side metadata contains a condition that part of themetadata is required to be handled as dynamic data, and a dynamichandling condition, and

the data flow control command includes the dynamic handling condition,and includes an instruction to instruct, if the sensing data that can behandled as dynamic data and is output by the sensor or data that can behandled as dynamic data and is output by another sensor attached to thissensor satisfies the dynamic handling condition, the correspondingsensor to transmit the sensing data to the application.

Appendix 2

A control method comprising:

a first acquiring step of acquiring sensor-side metadata, which isinformation relating to a sensor that can output sensing data;

a second acquiring step of acquiring application-side metadata, which isinformation relating to an application that uses the sensing data;

a comparing step of executing matching between the sensor-side metadataand the application-side metadata, and extracting a sensor that canprovide sensing data that meets a request of the application; and

an instructing step of transmitting, to a sensor management device thatmanages the sensor, a data flow control command that includesinformation that can specify the sensor extracted by the comparisonunit, and the application,

wherein the sensor-side metadata contains information that designatespart of the metadata as being able to be handled as dynamic data,

the application-side metadata contains a condition that part of themetadata is required to be handled as dynamic data, and a dynamichandling condition,

the data flow control command includes the dynamic handling condition,and includes an instruction to instruct, if the sensing data that can behandled as dynamic data and is output by the sensor or data that can behandled as dynamic data and is output by another sensor attached to thissensor satisfies the dynamic handling condition, the correspondingsensor to transmit the sensing data to the application.

Appendix 3

A sensor management device comprising:

a memory in which a receiving unit configured to receive sensing dataoutput by a sensor, and a transmitting unit capable of transmitting thereceived sensing data to an application that uses the sensing data arestored; and

a hardware processor connected to the memory,

wherein the hardware processor is configured to:

-   -   receive the sensing data output by the sensor;    -   transmit the received sensing data to an application that uses        the sensing data; and    -   receive a data flow control command that includes information        that can specify the application and the sensor that is        extracted through matching between sensor-side metadata, which        is information relating to a sensor that can output the sensing        data, and application-side metadata, which is information        relating to an application that uses the sensing data, and

wherein the sensor-side metadata contains information that designatespart of the metadata as being able to be handled as dynamic data,

the application-side metadata contains a condition that part of themetadata is required to be handled as dynamic data, and a dynamichandling condition,

the data flow control command includes the dynamic handling condition,and

in the transmitting step, if the sensing data that can be handled asdynamic data and is output by the sensor or data that can be handled asdynamic data and is output by another sensor attached to this sensorsatisfies the dynamic handling condition, the sensing data istransmitted to the application.

Appendix 4

A sensor management method comprising:

a receiving step of receiving sensing data output by a sensor; and

a transmitting step capable of transmitting the received sensing data toan application that uses the sensing data,

wherein, in the receiving step, a data flow control command is received,the data flow control command including information that can specify theapplication and the sensor that is extracted through matching betweensensor-side metadata, which is information relating to a sensor that canoutput the sensing data, and application-side metadata, which isinformation relating to an application that uses the sensing data,

the sensor-side metadata contains information that designates part ofthe metadata as being able to be handled as dynamic data,

the application-side metadata contains a condition that part of themetadata is required to be handled as dynamic data, and a dynamichandling condition,

the data flow control command includes the dynamic handling condition,and

in the transmitting step, if the sensing data that can be handled asdynamic data and is output by the sensor or data that can be handled asdynamic data and is output by another sensor attached to this sensorsatisfies the dynamic handling condition, the sensing data istransmitted to the application.

REFERENCE SIGNS LIST

1 Data providing system

2 Control device

20 Communication unit (first acquiring unit, second acquiring unit)

21 Control unit

22 Comparison unit

23 Generation unit

24 Notification unit

25 Sensor-side metadata storage unit

26 Application-side metadata storage unit

27 Contract state management unit

3 Sensor management device

30 Communication unit

31 Determination unit

32 Detection unit

33 Delivery unit

34 Sensing data storage unit

4 Sensor

5 Application server

6 NW

7 Another sensor

8 Mobile object

80 Network adapter

1. A control device comprising: a first acquiring unit configured toacquire sensor-side metadata, which is information relating to a sensorthat can output sensing data; a second acquiring unit configured toacquire application-side metadata, which is information relating to anapplication that uses the sensing data; a comparison unit configured toexecute matching between the sensor-side metadata and theapplication-side metadata, and extract a sensor that can provide sensingdata that meets a request of the application; and an instruction unitconfigured to transmit, to a sensor management device that manages thesensor, a data flow control command that includes information that canspecify the sensor extracted by the comparison unit, and theapplication; wherein the sensor-side metadata contains information thatdesignates part of the metadata as being able to be handled as dynamicdata, the application-side metadata contains a condition that part ofthe metadata is required to be handled as dynamic data, and a dynamichandling condition, and the data flow control command includes thedynamic handling condition, and includes an instruction to instruct, ifthe sensing data that can be handled as dynamic data and is output bythe sensor or data that can be handled as dynamic data and is output byanother sensor attached to this sensor satisfies the dynamic handlingcondition, the corresponding sensor to transmit the sensing data to theapplication.
 2. The control device according to claim 1, wherein thecomparison unit executes matching between a static component containedin the sensor-side metadata and the application-side metadata, andextracts the sensor that can provide the sensing data that meets therequest of the application, and the instruction unit transmits, to thesensor management device, a data flow control command that includes adynamic component of the sensor-side metadata that can be used todetermine whether or not the sensing data satisfies the handlingcondition.
 3. The control device according to claim 1, wherein thecomparison unit extracts a plurality of candidates for the sensor thatcan provide the sensing data that meets the request of the application,and the data flow control command includes an instruction to instructany of the plurality of candidates to transmit the sensing data thatsatisfies the handling condition to the application.
 4. The controldevice according to claim 1, wherein, if the application-side metadatamatches a plurality of pieces of sensor-side metadata, the instructionunit transmits the data flow control command to a plurality of sensormanagement devices that correspond to the respective pieces ofsensor-side metadata.
 5. The control device according to claim 4,wherein, if the sensor managed by one of the plurality of sensormanagement devices transmits the sensing data, the instruction unitnotifies the remaining at least one sensor management device ofcancellation of the instruction to deliver the sensing data.
 6. Thecontrol device according to claim 1, wherein the metadata contains ameasurement item of the sensor that is handled as dynamic data.
 7. Asensor management device comprising: a receiving unit configured toreceive sensing data output by a sensor; and a transmitting unit capableof transmitting the received sensing data to an application that usesthe sensing data, wherein the receiving unit receives a data flowcontrol command that includes information that can specify theapplication and the sensor that is extracted through matching betweensensor-side metadata, which is information relating to a sensor that canoutput the sensing data, and application-side metadata, which isinformation relating to an application that uses the sensing data, thesensor-side metadata contains information that designates part of themetadata as being able to be handled as dynamic data, theapplication-side metadata contains a condition that part of the metadatais required to be handled as dynamic data, and a dynamic handlingcondition, the data flow control command includes the dynamic handlingcondition, and if the sensing data that can be handled as dynamic dataand is output by the sensor or data that can be handled as dynamic dataand is output by another sensor attached to this sensor satisfies thedynamic handling condition, the transmitting unit transmits the sensingdata to the application.
 8. The sensor management device according toclaim 7, wherein the receiving unit is capable of receiving sensing dataoutput by a plurality of sensors, the transmitting unit transmits, outof the sensing data that can be handled as dynamic data and is output bythe sensors and the data that can be handled as dynamic data and isoutput by the other sensors attached to these sensors, sensing data thatsatisfies the dynamic handling condition to the application.
 9. Thesensor management device according to claim 7, further comprising, astorage unit configured to store the sensing data received by thereceiving unit, the sensing data being the sensing data that can behandled as dynamic data and is output by the sensor, or the data thatcan be handled as dynamic data and is output by the other sensorattached to this sensor, wherein the transmitting unit transmits thesensing data that satisfies the dynamic handling condition to theapplication, with reference to the storage unit.
 10. The sensormanagement device according to claim 7, further comprising, a detectionunit configured to detect that the sensing data received by thereceiving unit satisfies the dynamic handling condition, the sensingdata being the sensing data that can be handled as dynamic data and isoutput by the sensor, or the data that can be handled as dynamic dataand is output by the other sensor attached to this sensor, wherein, ifit is detected by the detection unit that the dynamic handling conditionis satisfied, the transmitting unit transmits the sensing data thatsatisfies the dynamic handling condition to the application.
 11. Thesensor management device according to claim 7, wherein, if the sensingdata that satisfies the dynamic handling condition is transmitted to theapplication, the transmitting unit notifies a control device thattransmitted the data flow control command of the transmission of thesensing data.
 12. A control method comprising: a first acquiring step ofacquiring sensor-side metadata, which is information relating to asensor that can output sensing data; a second acquiring step ofacquiring application-side metadata, which is information relating to anapplication that uses the sensing data; a comparing step of executingmatching between the sensor-side metadata and the application-sidemetadata, and extracting a sensor that can provide sensing data thatmeets a request of the application; and an instructing step oftransmitting, to a sensor management device that manages the sensor, adata flow control command that includes information that can specify thesensor extracted by the comparison unit, and the application, whereinthe sensor-side metadata contains information that designates part ofthe metadata as being able to be handled as dynamic data, theapplication-side metadata contains a condition that part of the metadatais required to be handled as dynamic data, and a dynamic handlingcondition, the data flow control command includes the dynamic handlingcondition, and includes an instruction to instruct, if the sensing datathat can be handled as dynamic data and is output by the sensor or datathat can be handled as dynamic data and is output by another sensorattached to this sensor satisfies the dynamic handling condition, thecorresponding sensor to transmit the sensing data to the application.13. (canceled)
 14. (canceled)
 15. (canceled)
 16. The control deviceaccording to claim 2, wherein the comparison unit extracts a pluralityof candidates for the sensor that can provide the sensing data thatmeets the request of the application, and the data flow control commandincludes an instruction to instruct any of the plurality of candidatesto transmit the sensing data that satisfies the handling condition tothe application.
 17. The control device according to claim 2, wherein,if the application-side metadata matches a plurality of pieces ofsensor-side metadata, the instruction unit transmits the data flowcontrol command to a plurality of sensor management devices thatcorrespond to the respective pieces of sensor-side metadata.
 18. Thecontrol device according to claim 3, wherein, if the application-sidemetadata matches a plurality of pieces of sensor-side metadata, theinstruction unit transmits the data flow control command to a pluralityof sensor management devices that correspond to the respective pieces ofsensor-side metadata.
 19. The sensor management device according toclaim 8, further comprising, a detection unit configured to detect thatthe sensing data received by the receiving unit satisfies the dynamichandling condition, the sensing data being the sensing data that can behandled as dynamic data and is output by the sensor, or the data thatcan be handled as dynamic data and is output by the other sensorattached to this sensor, wherein, if it is detected by the detectionunit that the dynamic handling condition is satisfied, the transmittingunit transmits the sensing data that satisfies the dynamic handlingcondition to the application.
 20. The sensor management device accordingto claim 9, further comprising, a detection unit configured to detectthat the sensing data received by the receiving unit satisfies thedynamic handling condition, the sensing data being the sensing data thatcan be handled as dynamic data and is output by the sensor, or the datathat can be handled as dynamic data and is output by the other sensorattached to this sensor, wherein, if it is detected by the detectionunit that the dynamic handling condition is satisfied, the transmittingunit transmits the sensing data that satisfies the dynamic handlingcondition to the application.
 21. The sensor management device accordingto claim 8, wherein, if the sensing data that satisfies the dynamichandling condition is transmitted to the application, the transmittingunit notifies a control device that transmitted the data flow controlcommand of the transmission of the sensing data.
 22. The sensormanagement device according to claim 9, wherein, if the sensing datathat satisfies the dynamic handling condition is transmitted to theapplication, the transmitting unit notifies a control device thattransmitted the data flow control command of the transmission of thesensing data.
 23. The sensor management device according to claim 10,wherein, if the sensing data that satisfies the dynamic handlingcondition is transmitted to the application, the transmitting unitnotifies a control device that transmitted the data flow control commandof the transmission of the sensing data.